home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-04-16 | 1.5 KB | 43 lines | [TEXT/GEOL] |
- Item forwarded by A33 to A34
-
- Item 0969677 13-April-90 01:41PDT
-
- From: D0416 Futuresoft System Design,PRT
-
- To: POWERUP.ENG Power Up Software,PRT
-
- cc: MACAPP.TECH$ MacApp Technical
-
- Sub: RE- None
-
- James,
-
- RE: PostCommand in TCmdButton.Trackmouse or TCmdButton.DoChoice?
-
- I say DoChoice. Why? Because in the true spirit of MacApp, always bypass doing
- any real work until you absolutely have to:-).
-
- But seriously, I like calling PostCommand in DoChoice better than Trackmouse
- because:
-
- 1) TrackMouse should really ONLY be concerned with… _tracking_the_mouse_, not
- posting commands. Yes, you can change the “current” command in a
- TView.TrackMouse but that should usually be done based on decisions done while
- _tracking_the_mouse_.
-
- Usually you are NOT changing commands while mouse tracking and you should delay
- posting a command until DoChoice is called. This also allows you to override
- TrackMouse easily without worrying also about posting commands.
-
- 2) If I was looking to see what TCmdButton does, I would first look at
- TCmdButton.DoChoice (NOT TrackMouse) because the method’s name sounds like
- something is going to be done there. [Again, in the true spirit of MacApp,
- nothing really would be DONE and we would simply instantiate and post another
- object (a TCommand) to bypass doing any real work (g)] But I think you get the
- idea.
-
- Just an opinion, I post,
- Ken_Addison.PostCommand(aCloseLinkCmd)
- FutureSoft System Designs, Inc.
-
-